|
FAQ - Features we will not implement
What is this NODO document?
This is a list of Feature Requests we get repeatedly that we simply cannot do on certain models of players. View it as the opposite of a TODO! This NODO document is currently organized in two sections: (1) features we will not or cannot implement on any players, and (2) features that we will not or cannot implement on Archos players.
Features we will not implement on any line of players
Interfacing with other USB devices (like cameras) or 2 player games over USB (sometimes known as USB On-The-Go or USBOTG)
The USB system demands that there is a master that talks to a slave. The Archos and iriver H120/H140, like most other USB devices, can only serve as a slave. Thus, without a master no communication between the slaves can take place.
If that is not enough, we have no ways of actually controlling the communication performed over USB since the USB circuit in the Archos is strictly made for disk-access and does not allow us to play with it the way we'd need for any good communication to work.
EXCEPTION: Certain newer players (i.e., the international version of the iriver H300) are capable of acting as a master. We may implement USBOTG on players on Rockbox ports to such players. As a general rule, if your player does not support USB OTG with its original firmware, Rockbox will not be able to support it either.
Support other filesystems than FAT32 (like NTFS or ext2 or whatever)!
Rockbox needs to support FAT32 since it can only start off a FAT32 partition (since that is the only way the ROM can load it), and adding support for more filesystems will just take away valueable ram for unnecessary features.
You can partition your player fine, just make sure the first one is FAT32 and then make the other ones whatever file system you want. Just don't expect Rockbox to understand them.
Add scandisk-like features!
It would be a very slow operation that would drain the batteries and take a lot of useful ram for something that is much better and faster done when connected to a host computer.
Features that we will not or cannot implement on the Archos line of players
Record to WAV (uncompressed) or MP3pro format!
The recording hardware (the MAS) does not allow us to do this.
Crossfade between tracks!
Crossfading would require two mp3 decoders, and we only have one. This is not possible.
Support MP3pro, WMA or other sound format playback!
The mp3-decoding hardware can only play MP3. We cannot make it play other sound formats.
Converting Ogg->MP3
The mp3-decoding hardware cannot decode Ogg. It can be reprogrammed, but there is too little memory for Ogg and we have no documentation on how to program the MAS's DSP.
Doing the conversion with the CPU is impossible, since a 12MHz SH1 is far too slow for this daunting task.
Archos Multimedia/Gmini support!
The Archos Multimedia is a completely different beast. It is an entirely different architecture, different CPU and upgrading the software is done a completely different way. We are not actively working with this.
See NonArchos for the latest status on Rockbox for non-SH1 Archos players.
Multi-band equalizer!
The MAS only offers the standard bass/treble settings and we can't do anything about it.
CBR recording!
The MP3 encoding hardware does not allow this.
Change tempo of a song without changing pitch!
The MP3 decoding hardware does not allow this.
Graphic frequency (spectrum) analyzer!
We can't access the audio waveform from the MP3 decoder so we can't analyze it. Even if we had access to it, the CPU would probably be too slow to perform the analysis anyway.
Cool sound effects!
Adding new sound effects requires reprogramming the MAS chip, and we can't do that. The MAS chip is programmable, but we have no access to the chip documentation.
CategoryFAQ: Features we will not implement
Revision r1.11 - 20 Aug 2005 - 05:16 GMT - JensArnold Parents: RockboxFAQ
|
Copyright © 1999-2005 by the contributing authors.
|
|
|